Skip to main content

This is a new service – your feedback will help us to improve it.

Calderdale Metropolitan Borough Council

Tree preservation zone

There is a problem

  • 453 entries with tree-preservation-order field must match the reference field in the tree preservation order dataset

Land off New Lane, Skircoat Green, Halifax.

reference
96/00951/C/1
name
Land off New Lane, Skircoat Green, Halifax.
tree-preservation-order

undefined

96/00951/C
tree-preservation-zone-type
group
geometry
MULTIPOLYGON (((-1.866754 53.703275,-1.866740 53.703257,-1.866261 53.703266,-1.866230 53.703256,-1.866239 53.703226,-1.866234 53.703213,-1.866245 53.703133,-1.866246 53.703026,-1.866211 53.702859,-1.866170 53.702816,-1.866099 53.702787,-1.866062 53.702840,-1.866027 53.702959,-1.866028 53.703045,-1.866067 53.703168,-1.866153 53.703290,-1.866754 53.703275)),((-1.868633 53.702484,-1.868401 53.702429,-1.868042 53.702367,-1.867440 53.702289,-1.867008 53.702166,-1.866644 53.702046,-1.866541 53.702214,-1.866544 53.702226,-1.866556 53.702231,-1.866929 53.702328,-1.866858 53.702437,-1.866974 53.702466,-1.867187 53.702493,-1.867345 53.702526,-1.867473 53.702564,-1.867541 53.702602,-1.867597 53.702720,-1.867628 53.702766,-1.867745 53.702768,-1.867744 53.702790,-1.867857 53.702781,-1.867863 53.702746,-1.867853 53.702734,-1.867883 53.702688,-1.867967 53.702630,-1.868050 53.702609,-1.868106 53.702625,-1.868136 53.702678,-1.868152 53.702730,-1.868504 53.702698,-1.868633 53.702484)))
point
POINT (-1.867424 53.702532)
notes
Beech, elm, hawthorn, holly, horse chestnut, lime, sycamore
entry-date
1996-08-16
start-date
1996-08-16
end-date

How to fix this issue

Your dataset is missing the tree-preservation-order column.

The Tree preservation zone guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that covers this zone.

How to improve Calderdale Metropolitan Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL